docs: 6-phase production path + version↔phase mapping#47
Merged
Conversation
PRODUCTION-PATH.adoc is the strategic long-form: where we are, what each phase delivers, what gate must be met to advance, the six load-bearing decisions due in the first year, and a comparison landscape locating typed-wasm against MS-Wasm / CHERI-Wasm / wasmGC / AssemblyScript / Rust / CompCert at each maturity level. ROADMAP.adoc now opens with an explicit mapping from its version-axis milestones (v0.1 ... v3.x) to PRODUCTION-PATH's phase-axis (Phase 0 ... Phase 6) so the two views stay coherent: version cuts can happen mid-phase; phase transitions usually need several version cuts to accumulate. README.adoc Status section now points readers at PRODUCTION-PATH for the bigger picture rather than describing it inline. No code changes. Out-of-scope for this commit: opening the per-phase tracking issues; that lands as a separate operation.
30 tasks
🔍 Hypatia Security ScanFindings: 119 issues detected
View findings[
{
"reason": "Issue in quality.yml",
"type": "missing_workflow",
"file": "quality.yml",
"action": "create",
"rule_module": "workflow_audit",
"severity": "high"
},
{
"reason": "Issue in security-policy.yml",
"type": "missing_workflow",
"file": "security-policy.yml",
"action": "create",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Action hyperpolymath/standards/.github/workflows/governance-reusable.yml@main needs attention",
"type": "unpinned_action",
"file": "governance.yml",
"action": "pin_sha",
"rule_module": "workflow_audit",
"severity": "high"
},
{
"reason": "Action actions/upload-artifact@v4 needs attention",
"type": "unpinned_action",
"file": "release.yml",
"action": "pin_sha",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Action actions/download-artifact@v4 needs attention",
"type": "unpinned_action",
"file": "release.yml",
"action": "pin_sha",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "believe_me undermines formal verification (1 occurrences, CWE-704)",
"type": "believe_me",
"file": "/home/runner/work/typed-wasm/typed-wasm/src/abi/TypedWasm/ABI/SessionProtocol.idr",
"action": "flag",
"rule_module": "code_safety",
"severity": "critical"
},
{
"reason": "assert_total bypasses totality checker (1 occurrences, CWE-704)",
"type": "assert_total",
"file": "/home/runner/work/typed-wasm/typed-wasm/src/abi/TypedWasm/ABI/SessionProtocol.idr",
"action": "flag",
"rule_module": "code_safety",
"severity": "high"
},
{
"reason": "believe_me undermines formal verification (1 occurrences, CWE-704)",
"type": "believe_me",
"file": "/home/runner/work/typed-wasm/typed-wasm/src/abi/TypedWasm/ABI/Echo.idr",
"action": "flag",
"rule_module": "code_safety",
"severity": "critical"
},
{
"reason": "assert_total bypasses totality checker (1 occurrences, CWE-704)",
"type": "assert_total",
"file": "/home/runner/work/typed-wasm/typed-wasm/src/abi/TypedWasm/ABI/Echo.idr",
"action": "flag",
"rule_module": "code_safety",
"severity": "high"
},
{
"reason": "believe_me undermines formal verification (1 occurrences, CWE-704)",
"type": "believe_me",
"file": "/home/runner/work/typed-wasm/typed-wasm/src/abi/TypedWasm/ABI/ResourceCapabilities.idr",
"action": "flag",
"rule_module": "code_safety",
"severity": "critical"
}
]Powered by Hypatia Neurosymbolic CI/CD Intelligence |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
docs/PRODUCTION-PATH.adocas the canonical 6-phase strategic plan from pre-alpha to production-ready, with explicit gates, load-bearing decisions, and a comparison landscape locating typed-wasm against MS-Wasm / CHERI-Wasm / wasmGC / AssemblyScript / Rust / CompCert at each maturity level.ROADMAP.adocnow opens with a version-axis ↔ phase-axis mapping so the two stay coherent (version cuts can happen mid-phase; phase transitions usually need several version cuts to accumulate).README.adocStatus section now points readers at PRODUCTION-PATH.What's in the plan
.twasm → .wasmround-trips for all examplesAlso documents the six load-bearing decisions due in the first year (bytecode vs. compile-to-wasm; producer-side-only vs. runtime-aware; W3C CG vs. independent; Idris2-only vs. dual proof implementation; MPL-2.0 vs. dual-license; single-maintainer vs. recruit committers).
Scope clarification
The plan explicitly targets "serious-systems compile target adopted outside hyperpolymath" — not "W3C-standardized bytecode peer to wasm" (different project) and not "own bytecode that runtimes execute natively" (out of scope).
Out of scope for this PR
Test plan
docs/PRODUCTION-PATH.adocrenders as valid AsciiDocLEVEL-STATUS.md, ECHIDNA results, or existing ADRsGenerated by Claude Code